rdar://132024975

Summary

Today DocC Render displays a beta badge for symbols that were introduced in the current version of a platform, if the platform's availability was set as beta in the DocC compiler command line invocation.

This change updates this heuristic to consider symbols that were introduced in the current - or future - version of a beta platform. This gives DocC a bit more flexibility to handle symbol data that might describe future versions of a platform, and to handle platforms that might have two versions in beta at the same time.

Dependencies

None.

Testing

Steps:

1. Build some API reference documentation containing at least one symbol with availability information. For example, a symbol might have this availability:

 "availability": [
    {
      "domain": "myPlatform",
      "introduced": {
        "major": 3,
        "minor": 0,
        "patch": 0
      }
    }
  ]

2. Declare this platform ("myPlatform") is beta using a DocC command line argument: --platform name=myPlatform,version=3.0.0,beta=true
3. View the symbol’s documentation page, and validate DocC marks it as beta; for example: myPlatform 3.0+ Beta
4. Now change the CLI argument and pass in an earlier version of the beta platform, for example: --platform name=myPlatform,version=1.0.0,beta=true
5. Recompile the documentation, and validate the symbol is still shown as beta: myPlatform 3.0+ Beta, even though the symbol was introduced in a later version of the beta platform.

Checklist

Make sure you check off the following items. If they cannot be completed, provide a reason.

• [ x] Added tests
• [x ] Ran the ./bin/test script and it succeeded
• [ ] Updated documentation if necessary